Messaging application sticker extensions

ABSTRACT

Systems and methods are provided for performing operations including: receiving, with a messaging application implemented by one or more processors of a user device, a communication from a given application representing a first user interaction with the given application; generating, with the messaging application, a list of graphical elements based on the communication received from the given application; displaying, with the messaging application, the list of graphical elements; receiving, with the messaging application, a user selection of a first graphical element from the list of graphical elements; and incorporating, with the messaging application, the graphical element selected by the user into a message for transmission to another user.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority of U.S. ProvisionalPatent Application Number 62/908,332, entitled “MESSAGING APPLICATIONSTICKER EXTENSIONS,” filed on Sep. 30, 2019 (Attorney Docket No.4218.859PRV), the entirety of which is hereby incorporated by referenceherein.

TECHNICAL FIELD

The present disclosure relates generally to providing graphical elementsusing a messaging application.

BACKGROUND

Modern day user devices provide messaging applications that allow usersto exchange messages with one another. Such messaging applications haverecently started incorporating graphics in such communications. Userscan select between various predetermined graphics to incorporate intotheir communications.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. To easily identifythe discussion of any particular element or act, the most significantdigit or digits in a reference number refer to the figure number inwhich that element is first introduced. Some embodiments are illustratedby way of example, and not limitation, in the figures of theaccompanying drawings in which:

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network,according to example embodiments.

FIG. 2 is a schematic diagram illustrating data which may be stored inthe database of a messaging server system, according to exampleembodiments.

FIG. 3 is a schematic diagram illustrating a structure of a messagegenerated by a messaging client application for communication, accordingto example embodiments.

FIG. 4 is a block diagram showing an example graphical element selectionsystem, according to example embodiments.

FIG. 5 is a flowchart illustrating example operations of the graphicalelement selection system, according to example embodiments.

FIGS. 6-8 are illustrative inputs and outputs of the graphical elementselection system, according to example embodiments.

FIG. 9 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described, according to example embodiments.

FIG. 10 is a block diagram illustrating components of a machine able toread instructions from a machine-readable medium (e.g., amachine-readable storage medium) and perform any one or more of themethodologies discussed. herein, according to example embodiments.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments. It will be evident, however, to those skilled in the art,that embodiments may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

Typically, users exchange messages with each other using messagingapplications. Such applications allow users to select from a predefinedlist of images and avatars to send to one another. Users areincreasingly communicating with each other using such images and avatarsto convey their thoughts. However, finding the right images or avatarsto convey a particular thought can be tedious and time consuming.Specifically, the user has to manually search using keywords for aparticular image or avatar that conveys a given message. This requiresnavigating through multiple pages of information until the desired imageor avatar is found. Given the complexity and amount of time it takes tofind the right image or avatar, users become discouraged fromcommunicating using the images or avatars, which results in a waste ofresources or lack of use.

Also, sometimes users are performing an activity on an application, suchas an exercise or music application. If the user would like to sharethat activity with another user by sending an image or avatar throughthe messaging application, the user is forced to search through hundredsof images or avatars in the messaging application to find one that issuitable to share with the other user. Even still, the images or avatarsavailable through the messaging application are typically of genericform and may not accurately reflect activities performed on otherapplications.

The disclosed embodiments improve the efficiency of using the electronicdevice by providing a system that intelligently selects and presentsgraphical elements for a user to send others in a messaging applicationbased on activities a user performs with other applications.Specifically, according to the disclosed embodiments, a messagingapplication implemented by one or more processors of a user devicereceives a communication from a given application representing a firstuser interaction with the given application. The messaging applicationgenerates a list of graphical elements based on the communicationreceived from the given application and displays that list of graphicalelements. The messaging application receives a user selection of a firstgraphical element from the list of graphical elements and incorporatesthe graphical element selected by the user into a message fortransmission to another user.

In some embodiments, the list of graphical elements is dynamicallyordered based on the first user interaction with the given application.Specifically, the messaging application receives another communicationfrom the given application representing a second user interaction withthe given application and determines that the second user interactiontook place more recently than the first user interaction. In response todetermining that the second user interaction took place more recentlythan the first user interaction, the messaging application positions asecond graphical element in the list of graphical elements associatedwith the first user interaction at a lower position in the list ofgraphical elements than a third graphical element associated with thesecond user interaction. As an example, the first user interactionrepresents a first song played by the given application, the second userinteraction represents a second song played by the given applicationafter the first song, the second graphical element identifies the firstsong, and the third graphical element identifies the second song.

In this way, the disclosed embodiments improve the efficiency of usingthe electronic device by reducing the number of screens and interfaces auser has to navigate through to find a graphical element to share withother users. This is done by receiving a communication from a connectedapplication with the messaging application that represents user activitywith the connected application and/or includes a graphical elementgenerated by the connected application. The connected application can bea third-party application that is provided by an entity or organizationthat differs from the entity or organization that provides the messagingapplication. This reduces the device resources (e.g., processor cycles,memory, and power usage) needed to accomplish a task with the device.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network106. The messaging system 100 includes multiple client devices 102, eachof which hosts a number of applications, including a messaging clientapplication 104 and a third-party application 105. Each messaging clientapplication 104 is communicatively coupled to other instances of themessaging client application 104, the third-party application 105, and amessaging server system 108 via a network 106 (e.g., the Internet).

Accordingly, each messaging client application 104 and third-partyapplication 105 is able to communicate and exchange data with anothermessaging client application 104 and third-party applications) 105 andwith the messaging server system 108 via the network 106. The dataexchanged between messaging client applications 104, third-partyapplications 105, and between a messaging client application 104 and themessaging server system 108 includes Functions (e.g., commands to invokefunctions) and payload data (e.g., text, audio, video, or othermultimedia data). Any disclosed communications between the messagingclient application 104 and the third-party application(s) 105 can betransmitted directly from the messaging client application 104 to thethird-party application(s) 105 and/or indirectly (e.g., via one or moreservers) from the messaging client application 104 to the third-partyapplication(s) 105.

The third-party application(s) 105 and the messaging client application104 are applications that include a set of functions that allow theclient device 102 to access a graphical element selection system 124.The third-party application 105 is an application that is separate anddistinct from the messaging client application 104. The third-partyapplication(s) 105 are downloaded and installed by the client device 102separately from the messaging client application 104. In someimplementations, the third-party application(s) 105 are downloaded andinstalled by the client device 102 before or after the messaging clientapplication 104 is downloaded and installed. The third-party application105 is an application that is provided by an entity or organization thatis different from the entity or organization that provides the messagingclient application 104. The third-party application 105 is anapplication that can be accessed by a client device 102 using separatelogin credentials than the messaging client application 104. Namely, thethird-party application 105 can maintain a first user account and themessaging client application 104 can maintain a second user account. Inan embodiment, the third-party application 105 can be accessed by theclient device 102 to perform various activities and interactions, suchas listening to music, videos, track exercises, view graphical elements(e.g., stickers), communicate with other users, and so forth.

As an example, the third-party application 105 can be a socialnetworking application, a dating application, a ride or car sharingapplication, a shopping application, a trading application, a gamingapplication, an imaging application, a music application, a videobrowsing application, an exercise tracking application, a healthmonitoring application, a graphical element or sticker browsingapplication, or any other suitable application.

In some embodiments, the third-party application 105 is configured toshare authentication information with the messaging client application104. For example, the third-party application 105 can shareauthentication information with the messaging client application 104based on the OAuth 2 flow framework. After the third-party application105 is configured to share authentication information with the messagingclient application 104 (e.g., after a user selects an option to connectthe third-party application 105 with the messaging client application104), the third-party application 105 can transmit one or morecommunications to the messaging client application 104. Suchcommunications can include graphical elements or stickers generated bythe third-party application 105 and/or contextual data representing userinteractions with the third-party application 105. For example, thethird-party application 105 may be a music application that transmits tothe messaging client application 104 graphical elements representingmusic listened to by the user on the third-party application 105.Alternatively, the third-party application 105 may be a musicapplication that transmits to the messaging client application 104 datarepresenting music listened to by the user on the third-partyapplication 105. The messaging client application 104 may then generatea list of graphical elements that include the graphical elementsreceived from the third-party application 105 and/or that includegraphical elements selected based on the information received from thethird-party application 105.

To connect the third-party application 105 with the messaging clientapplication 104, the messaging client application 104 presents agraphical user interface to a user that lists third-party applications105 that are configured to be connected to the messaging clientapplication 104. In an embodiment, this list may include only thoseapplications that can provide contextual information and/or graphicalelements to the messaging client application 104. After a user selectsan option to connect to one of the applications in the list ofthird-party applications 105, the messaging client application 104communicates an authentication token to an authentication server. Theauthentication token may include information from a user account withthe messaging client application 104. The authentication token mayuniquely identify the third-party application 105 selected by the userand may be associated with an expiration time. The third-partyapplication 105 communicates with the authentication server to obtainthe authentication token. Using the information contained in theauthentication token (e.g., a username, a password, a user address, andso forth), the third-party application 105 is able to provide the useraccess to features of the third-party application 105 and is able toshare information and transmit communications to the messaging clientapplication 104.

Namely, a user can launch the third-party application 105 and, inresponse, the third-party application 105 communicates with theauthentication server to determine whether the third-party application105 has a valid token for the user. If the expiration time specified inthe token has not yet been reached, the third-party application 105retrieves the token and logs the user into the third-party application105 using the information contained in the token. The third-partyapplication 105 also transmits communications to the messaging clientapplication 104 representing user interactions with the third-partyapplication 105. If the expiration time has been reached or exceeded,the third-party application 105 can request that the messaging clientapplication 104 renew the token to extend the expiration time. If themessaging client application 104 renews the token, the third-partyapplication 105 automatically logs the user into the third-partyapplication 105 and enables the user to access the features of thethird-party application 105.

In some embodiments, the messaging client application 104 receives oneor more communications from one or more third-party applications 105.The messaging client application 104 generates a list of graphicalelements based on the communications it receives from the one or morethird-party applications 105. The messaging client application 104displays the list of graphical elements to a user and receives a userselection of a first graphical element from the list of graphicalelements. In response to receiving the user selection, the messagingclient application 104 incorporates the graphical element selected bythe user into a message for transmission to another user.

As an example, the messaging client application 104 receives datarepresenting music listened to by a user of a music application. Thedata may include graphical elements (cover arts) of each music item theuser listened to and/or titles or identifiers of such music items. Themessaging client application 104 obtains a list of graphical elementsthat includes graphical elements generated by the messaging clientapplication 104 and graphical elements associated with other third-partyapplications 105. The messaging client application 104 adds one or moregraphical elements associated with the music application to the list ofgraphical elements.

In an embodiment, the messaging client application 104 adds thegraphical element (e.g., cover art) received from the music application.In an embodiment, the messaging client application 104 retrieves agraphical element based on the identifiers received from the musicapplication for addition to the list of graphical elements. In someembodiments, the messaging client application 104 receives datarepresenting exercise tracked by a user of an exercise application. Insuch cases, the exercise application provides a graphical elementrepresenting the exercise performed by the user and/or metric orstatistic information representing the exercise. For example, if theuser ran for 25 kilometers, the exercise application provides agraphical element showing a person running combined with text indicating25 kilometers.

The list of graphical elements is presented to the user in a dedicatedgraphical element browsing interface and/or in a chat interface. Inresponse to the user selecting a given graphical element from the list,the messaging client application 104 presents additional informationassociated with the graphical element and/or automatically sends thegraphical element to a designated recipient. In some embodiments, thegraphical elements include a universal resource locator (URL) whichretrieves additional content associated with the graphical element inresponse to selection of the graphical element. Specifically, thegraphical element may be interactive and when a recipient selects thegraphical element or when the sender of the graphical element selectsthe graphical element, the URL is used to retrieve additional content(e.g., a webpage, music, video, images, or other content) forpresentation to the user.

For example, if the user is in an active chat session with a second userand selects an option to view a list of graphical elements, the list ofgraphical elements may be presented to the user together with the chatmessages exchanged between the users. If the user selects a givengraphical element from the list, the messaging client application 104automatically sends the selected graphical element to the second userwith whom the user is in an active chat session. As another example, ifthe user is browsing graphical elements in a graphical element browsinginterface, the messaging client application 104 presents options forsending a selected graphical element to another user. Specifically, themessaging client application 104 presents a list of possible recipients(e.g., a user's friends) and automatically sends the selected graphicalelement to one or more users selected by the user from the presentedlist.

In some embodiments, the graphical elements presented by the messagingclient application 104 is dynamically ranked and ordered. In an example,the graphical elements are dynamically ranked and ordered based onrecency of the user interaction with the third-party application 105and/or based on time or other criteria. For example, a second graphicalelement in the list of graphical elements is in a first position in thelist of graphical elements at a first point in time and is positionedlower in the list of graphical elements at a second point in time laterthan the first point in time. Specifically, the messaging clientapplication 104 receives another communication from the third-partyapplication 105 representing a second user interaction with thethird-party application 105 and determines that the second userinteraction took place more recently than the first user interaction.For example, the second user interaction represents a first songlistened to by the user after or more recently than a second songlistened to by the user on a music application. In response, themessaging client application 104 positions a second graphical element inthe list of graphical elements associated with the first userinteraction at a lower position in the list of graphical elements than athird graphical element associated with the second user interaction.

In some embodiments, the messaging client application 104 presents thelist of graphical elements in different regions of a graphical userinterface, where each region is associated with a respective third-partyapplication 105. For example, the messaging client application 104presents a first set of the graphical elements in the list of graphicalelements in a first region dedicated to presenting graphical elementsassociated with a first third-party application 105 and presents asecond set of the graphical elements in the list of graphical elementsin a second region dedicated to presenting graphical elements associatedwith a second third-party application 105. In an embodiment, the regionsare dynamically ordered and positioned based on recency of receivingcommunications from the respective third-party applications 105. Forexample, if the messaging client application 104 receives acommunication from second third-party application 105 after receivingthe communication from the first third-party application 105, themessaging client application 104 may place the second region above orranked in a higher position than the first region. In someimplementations, the third-party application 105 provides rankinginformation for the graphical elements associated with the third-partyapplication 105. In such cases, the graphical elements presented by themessaging client application 104 in association with the third-partyapplication 105 are ranked based on the ranking information receivedfrom the third-party application 105.

In some embodiments, the messaging client application 104 presents agraphical user interface that allows the user to view applications(e.g., connected applications including third-party applications 105)that have been previously authorized by the messaging client application104 to share the authentication information from the messaging clientapplication 104. The graphical user interface may include an option foreach application that allows the user to instruct the messaging clientapplication 104 to discontinue sharing the authentication information.In response to the user selecting the option to discontinue sharing theauthentication information, the messaging client application 104 sends,to the authentication server, the specific identity of the third-partyapplication 105 that is associated with the selected option and anindication to expire or revoke the token for that application. At alater point, the user can select an option to reconnect the applicationthat has been disconnected, at which time the messaging clientapplication 104 communicates to the authentication server the specificidentity of the third-party application 105 that is associated with theselected option to reconnect and an indication to renew the token forthat application.

In some embodiments, features of the messaging client application 104are selectively enabled based on whether a given third-party application105 has been connected to the messaging client application 104. Forexample, a feature to share media items with other applications can bein a disabled state when the given third-party application 105 has notyet been connected to the messaging client application 104. In responseto the user selecting an option to share authentication information withthe third-party application 105, the feature to share media items withother applications, and particularly with the third-party application105, becomes enabled. The user can select and interact with the featureto automatically transmit to the third-party application 105 any mediaitems that are captured, stored, and manipulated by the messaging clientapplication 104. The third-party application 105, once connected, isconfigured to use an API of the messaging client application 104 todisplay or playback any of the media items that have been transmittedand shared with the third-party application 105 by the messaging clientapplication 104. Namely, the media items may be configured to only beplayed using a video or image player (decoder) of the messaging clientapplication 104 and the API enables the third-party application 105 toaccess the player of the messaging client application 104 to play themedia items. In this way, because playback of the media items by thethird-party application 105 is controlled by the API of the messagingclient application 104, the messaging client application 104 can computemetrics or a view count for each media item even when such a media itemis played or accessed by the third-party application 105 outside of themessaging client application 104. Specifically, a given media item maybe transmitted and shared by the messaging client application 104 withfirst and second third-party applications 105. If such a media item isplayed 100 times by users of a first third-party application 105 and 200times by users of a second third-party application 105 through the APIof the messaging client application 104, the messaging clientapplication 104 can track and determine that the view count of theparticular media item is 300, even though the media item was accessed bythe first and second third-party applications 105.

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality either within the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include message content, client device information, graphicalelements, geolocation information, media annotation and overlays,virtual objects, message content persistence conditions, social networkinformation, and live event information, as examples. Data exchangeswithin the messaging system 100 are invoked and controlled throughfunctions available via user interfaces (UIs) (e.g., graphical userinterfaces) of the messaging client application 104.

Turning now specifically to the messaging server system 108, an APIserver 110 is coupled to, and provides a programmatic interface to, anapplication server 112. The application server 112 is communicativelycoupled to a database server 118, which facilitates access to a database120 in which is stored data associated with messages processed by theapplication server 112

Dealing specifically with the API server 110, this server 110 receivesand transmits message data (e.g., commands and message payloads) betweenthe client device 102 and the application server 112. Specifically, theAPI server 110 provides a set of interfaces (e.g., routines andprotocols) that can be called or queried by the messaging clientapplication 104 and the third-party application 105 in order to invokefunctionality of the application server 112. The API server 110 exposesvarious functions supported by the application server 112, includingaccount registration; login functionality; the sending of messages, viathe application server 112, from a particular messaging clientapplication 104 to another messaging client application 104 orthird-party application 105; the sending of media files (e.g., graphicalelements, images or video) from a messaging client application 104 to amessaging server application 114, and for possible access by anothermessaging client application 104 or third-party application 105; agraphical element list; the setting of a collection of media data (e.g.,story); the retrieval of such collections; the retrieval of a list offriends of a user of a client device 102; the retrieval of messages andcontent; the adding and deleting of friends to a social graph; thelocation of friends within a social graph; access to user conversationdata; access to avatar information stored on messaging server system108; and opening an application event (e.g., relating to the messagingclient application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116, a social network system 122, and the graphicalelement selection system 124. The messaging server application 114implements a number of message processing technologies and functions,particularly related to the aggregation and other processing of content(e.g., textual and multimedia content) included in messages receivedfrom multiple instances of the messaging client application 104. As willbe described in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories or galleries). These collections are then made available, by themessaging server application 114, to the messaging client application104. Other processor- and memory-intensive processing of data may alsobe performed server-side by the messaging server application 114, inview of the hardware requirements for such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114. A portion of theimage processing system 116 may also be implemented by the graphicalelement selection system 124.

The social network system 122 supports various social networkingfunctions and services and makes these functions and services availableto the messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph within the database120. Examples of functions and services supported by the social networksystem 122 include the identification of other users of the messagingsystem 100 with which a particular user has relationships or is“following” and also the identification of other entities and interestsof a particular user. Such other users may be referred to as the user'sfriends. Social network system 122 may access location informationassociated with each of the user's friends to determine where they liveor are currently located geographically. Social network system 122 maymaintain a location profile for each of the user's friends indicatingthe geographical location where the user's friends live.

The graphical element selection system 124 generates a list of graphicalelements based on communications received from third-party applications105. In some embodiments, the graphical element selection system 124communicates with the third-party applications 105 in accordance withthe OAuth 2 flow framework. The graphical element selection system 124communicates with the third-party application 105 to receive acommunication (e.g., data or graphical elements) representing userinteractions with the third-party application 105. The graphical elementselection system 124 generates or modifies a list of graphical elementsbased on the received communication and presents the list of graphicalelements to a user for selection and incorporation into a messagetransmitted to another user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120, in which isstored data associated with messages processed by the messaging serverapplication 114. Database 120 may be a third-party database. Forexample, the application server 112 may be associated with a firstentity, and the database 120 or a portion of the database 120 may beassociated and hosted by a second different entity. In someimplementations, database 120 stores user data that the first entitycollects about various each of the users of a service provided by thefirst entity. For example, the user data includes user names, phonenumbers, passwords, addresses, friends, activity information,preferences, videos or content consumed by the user, and so forth.

FIG. 2 is a schematic diagram 200 illustrating data, which may be storedin the database 120 of the messaging server system 108, according tocertain example embodiments. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table214. An entity table 202 stores entity data, including an entity graph204. Entities for which records are maintained within the entity table202 may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the messaging server system 108 stores data may be a recognizedentity. Each entity is provided with a unique identifier, as well as anentity type identifier (not shown).

The entity graph 204 stores information regarding relationships andassociations between entities. Such relationships may be social,professional (e.g., work at a common corporation or organization),interest-based, or activity-based, merely for example.

Message table 214 may store a collection of conversations between a userand one or more friends or entities. Message table 214 may includevarious attributes of each conversation, such as the list ofparticipants, the size of the conversation (e.g., number of users and/ornumber of messages), the chat color of the conversation, a uniqueidentifier for the conversation, and any other conversation relatedfeature(s).

The database 120 also stores annotation data, in the example form offilters, in an annotation table 212. Database 120 also stores annotatedcontent received in the annotation table 212. Filters for which data isstored within the annotation table 212 are associated with and appliedto videos (for which data is stored in a video table 210) and/or images(for which data is stored in an image table 208). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of varioustypes, including user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters), which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a UI by the messaging client application 104, based ongeolocation information determined by a Global Positioning System (GPS)unit of the client device 102. Another type of filter is a data filter,which may be selectively presented to a sending user by the messagingclient application 104, based on other inputs or information gathered bythe client device 102 during the message creation process. Examples ofdata filters include current temperature at a specific location, acurrent speed at which a sending user is traveling, battery life for aclient device 102, or the current time.

Other annotation data that may be stored within the image table 208 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 210 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 214. Similarly, the image table 208 storesimage data associated with messages for which message data is stored inthe entity table 202. The entity table 202 may associate variousannotations from the annotation table 212 with various images and videosstored in the image table 208 and the video table 210.

Graphical element list 207 stores graphical elements generated by themessaging client application 104 and received from one or morethird-party applications 105. Each graphical element in the list 207 maybe associated with a time stamp that is used to reposition the graphicalelement in the graphical element list 207. Each graphical element in thelist 207 may be associated with an application identifier that is usedto position the graphical element in a graphical element displayinterface of the messaging client application 104. For example, theapplication identifier is used to place the graphical element in adedicated region of a display associated with the respectiveapplication.

Application list 209 stores a list of all applications installed on agiven client device 102. As new applications are installed on the givenclient device 102, the client device updates the application list 209with the name and identity of the installed application. Applicationlist 209 also stores a list of all the applications that are configuredto share authentication information with the messaging clientapplication 104 (e.g., applications that are connected with themessaging client application 104 and/or that can be selected to beconnected with the messaging client application 104).

A story table 206 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 202). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the UI of themessaging client application 104 may include an icon that isuser-selectable to enable a sending user to add specific content to hisor her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom various locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via a UIof the messaging client application 104, to contribute content to aparticular live story. The live story may be identified to the user bythe messaging client application 104 based on his or her location. Theend result is a “live story” told from a community perspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 3 is a schematic diagram illustrating a structure of a message 300,according to some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 300 is used to populate the message table 214stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 300 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 300 is shown to include thefollowing components:

-   -   A message identifier 302: a unique identifier that identifies        the message 300.    -   A message text payload 304: text, to be generated by a user via        a of the client device 102 and that is included in the message        300.    -   A message image payload 306: image data, captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102, and that is included in the message 300.    -   A message video payload 308: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 300.    -   A message audio payload 310: audio data, captured by a        microphone or retrieved from the memory component of the client        device 102, and that is included in the message 300.    -   Message annotations 312: annotation data (e.g., filters,        stickers, or other enhancements) that represents annotations to        be applied to message image payload 306, message video payload        308, or message audio payload 310 of the message 300.    -   A message duration parameter 314: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 306, message video payload 308,        message audio payload 310) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 316: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 316 values may be included in the payload, with each        of these parameter values being associated with respect to        content items included in the content (e.g., a specific image        within the message image payload 306, or a specific video in the        message video payload 308).    -   A message story identifier 318: identifier value identifying one        or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 306 of the        message 300 is associated. For example, multiple images within        the message image payload 306 may each be associated with        multiple content collections using identifier values.    -   A message tag 320: each message 300 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 306        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 320 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 322: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 300 was generated and from which the message        300 was sent.    -   A message receiver identifier 324: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of user(s) of the client device 102 to        which the message 300 is addressed. In the case of a        conversation between multiple users, the identifier may indicate        each user involved in the conversation.

The contents (e.g., values) of the various components of message 300 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 306 maybe a pointer to (or address of) a location within an image table 208.Similarly, values within the message video payload 308 may point to datastored within a video table 210, values stored within the messageannotations 312 may point to data stored in an annotation table 212,values stored within the message story identifier 318 may point to datastored in a story table 206, and values stored within the message senderidentifier 322 and the message receiver identifier 324 may point to userrecords stored within an entity table 202.

FIG. 4 is a block diagram showing an example graphical element selectionsystem 124, according to example embodiments. Graphical elementselection system 124 includes a third-party application communicationmodule 414, a graphical element list generation module 416, and amessage generation module 418.

Specifically, the third-party application communication module 414allows a user to select one or more third-party applications 105 toconnect to the messaging client application 104. As an example, a usermay access a graphical user interface of the messaging clientapplication 104 and request to search for third-party applications 105that are configured to share and provide graphical elements to themessaging client application 104. The third-party applicationcommunication module 414 searches a list of third-party applications 105that are installed on the user device to identify a set of thethird-party applications 105 that are configured to share and providegraphical elements to the messaging client application 104. To do so,the third-party application communication module 414 may access a liststored on a server that identifies all of the possible third-partyapplications 105 that are configured to share and provide graphicalelements to the messaging client application 104. Any application thatis installed on the user device that is also on the list of applicationsstored on the server may be identified by the third-party applicationcommunication module 414 for inclusion in the set of the third-partyapplications 105.

The third-party application communication module 414 presents the set ofthird-party applications 105 with possibly a description of eachapplication. Each application may be presented with a respective optionto connect to the third-party application 105. In response to receivinga user selection of the connect option for a given third-partyapplication 105, the third-party application communication module 414communicates with the given third-party application 105 to establish andshare authentication information in accordance with the OATH 2framework. Once the given third-party application 105 is connected, thethird-party application communication module 414 adds a respectivegraphical element display region to a list of graphical elements. Theadded graphical element display region may be configured to only displaygraphical elements from the given third-party application 105. Thethird-party application communication module 414 communicates with thegiven third-party application 105 to obtain an initial set of graphicalelements generated by the third-party application 105 and may add thatset of graphical elements to the graphical element display region of thegiven third-party application 105 that is displayed by the messagingclient application 104.

As the user interacts with the given third-party application 105, thegiven third-party application 105 communicates such interactions to thethird-party application communication module 414. As an example, thegiven third-party application 105 may be a music consumption applicationand the communications may identify an ordered list of music currentlybeing consumed or consumed by the user in the past. The communicationsmay include graphical elements for each song the user listens to on themusic consumption application. As another example, the given third-partyapplication 105 may be a video consumption application and thecommunications may identify an ordered list of videos currently beingconsumed or consumed by the user in the past. The communications mayinclude graphical elements for each video the user watches on the videoconsumption application. The music or video graphical elements may beinteractive and include respective URLs that allow another user toselect to access the corresponding video or music associated with thegraphical element. For example, if the user sends a graphical elementassociated with a first video to a second user, the second user can tapor click the graphical element and in response the URL is retrieved toview the first video. In an embodiment, the URL includes a play positionsuch that the second user accesses the video or music from the same playposition as the sender of the graphical element or from a play positionselected by the sender of the graphical element.

As another example, the given third-party application 105 may be anexercise application and the communications may include exercisecurrently performed or performed recently by the user and/or metrics orstatistics associated with the exercise. The exercise application maysend a graphical element representing the exercise and/or including themetrics or statistics to the third-party application communicationmodule 414. In some embodiments, the given third-party application 105(e.g., the exercise application) provides a duration of the userinteraction or the exercise performed by the user. The graphical elementlist generation module 416 may rank or order the graphical elementsbased on the duration of the user interaction, such that longer durationuser interactions cause respective graphical elements to be positionedhigher in the list than shorter duration user interactions.

As another example, the given third-party application 105 may be agraphical element search and generation application. In such cases, theuser may be using the graphical element search and generationapplication to search and find and/or to create specific graphicalelements. Such graphical elements are provided by the graphical elementsearch and generation application to the third-party applicationcommunication module 414 for inclusion in the list of graphical elementsgenerated by the graphical element list generation module 416. In someembodiments, the third-party applications 105 transmit identifiers ofthe graphical elements to the third-party application communicationmodule 414. The identifiers are used by the third-party applicationcommunication module 414 to search and retrieve a correspondinggraphical element from the list 207. In this way, the third-partyapplications 105 can manage the layout and display of graphical elementspresented by the messaging client application 104. This reduces theamount of resources consumed by the messaging client application 104 andincreases efficiency of the device.

The third-party application communication module 414 provides thegraphical elements or information about the user interactions to thegraphical element list generation module 416. In some embodiments, thegraphical element list generation module 416 accesses the list ofgraphical elements stored in list 207. The graphical element listgeneration module 416 adds and/or reorders the graphical elements in thelist of graphical elements based on the graphical elements and/or userinteractions received from the third-party applications 105. In anexample, the graphical element list generation module 416 places agraphical element representing a most recent user interaction above orranked higher than another graphical element. Specifically, thegraphical element list generation module 416 presents a graphicalelement representing a first song listened to after a second song aboveor higher ranked than the graphical element representing the secondsong.

In some embodiments, the graphical element list generation module 416presents the list of graphical elements in different regions of agraphical user interface, where each region is associated with arespective third-party application 105. For example, the graphicalelement list generation module 416 presents a first set of the graphicalelements in the list of graphical elements in a first region dedicatedto presenting graphical elements associated with a first third-partyapplication 105 and presents a second set of the graphical elements inthe list of graphical elements in a second region dedicated topresenting graphical elements associated with a second third-partyapplication 105. In an embodiment, the regions are dynamically orderedand positioned based on recency of receiving communications from therespective third-party applications 105. For example, if the graphicalelement list generation module 416 receives a communication from secondthird-party application 105 after receiving the communication from thefirst third-party application 105, the graphical element list generationmodule 416 may place the second region above or ranked in a higherposition than the first region. In some implementations, the third-partyapplication 105 provides ranking information for the graphical elementsassociated with the third-party application 105. In such cases, thegraphical elements in the list generated by the graphical element listgeneration module 416 in association with the third-party application105 are ranked based on the ranking information received from thethird-party application 105.

In some embodiments, the graphical element list generation module 416actively and dynamically modifies the graphical elements displayed inthe list of graphical elements to the user. For example, the graphicalelement list generation module 416 may remove graphical elements thatare older than a certain period of time (e.g., are older than 2 hours or1 day). In some embodiments, the graphical element list generationmodule 416 receives contextual information from the third-partyapplications 105 and orders the list of graphical elements based on thecontextual information. In some embodiments, contextual informationreceived from a first third-party application 105 is used to rearrangeor re-rank graphical elements associated with the first third-partyapplication 105 and graphical elements associated with a secondthird-party application 105. For example, the graphical element listgeneration module 416 may receive an indication from an exerciseapplication that the user completed a marathon. In response, thegraphical element list generation module 416 may select a graphicalelement representing a marathon run for presentation in the list ofgraphical elements of the exercise application. In addition, thegraphical element list generation module 416 may select a graphicalelement representing a movie about marathons for presentation in thelist of graphical elements of a video consumption application.

The graphical element list generation module 416 provides the generatedlist of graphical elements to the message generation module 418. Themessage generation module 418 presents the list of graphical elements inan active chat interface and/or in a graphical element browsinginterface. The message generation module 418 receives a user selectionof a graphical element that is displayed to the user and allows the userto compose a message for transmission to another user. In an example,the message generation module 418 presents the graphical elements in achat interface and selection of a graphical element from the listautomatically transmits the selected graphical element to a user withwhom the user is communicating in the chat interface. In anotherexample, the message generation module 418 presents the graphicalelements in a browsing interface. Selection of a graphical element inthe browsing interface allows the user to add the selected graphicalelement to an image or video and then send the image or video with theadded graphical element to a designated recipient.

FIG. 5 is a flowchart illustrating example operations of the graphicalelement selection system 124 in performing process 500, according toexample embodiments. The process 500 may be embodied incomputer-readable instructions for execution by one or more processorssuch that the operations of the process 500 may be performed in part orin whole by the functional components of the messaging server system 108and/or third-party application 105; accordingly, the process 500 isdescribed below by way of example with reference thereto. However, inother embodiments, at least some of the operations of the process 500may be deployed on various other hardware configurations. The process500 is therefore not intended to be limited to the messaging serversystem 108 and can be implemented in whole, or in part, by any othercomponent. Some or all of the operations of process 500 can be inparallel, out of order, or entirely omitted.

At operation 501, the graphical element selection system 124 receives acommunication from a given application representing a first userinteraction with the given application.

At operation 502, the graphical element selection system 124 generates alist of graphical elements based on the communication received from thegiven application.

At operation 503, the graphical element selection system 124 displaysthe list of graphical elements.

At operation 504, the graphical element selection system 124 receives auser selection of a first graphical element from the list of graphicalelements.

At operation 505, the graphical element selection system 124incorporates the graphical element selected by the user into a messagefor transmission to another user.

FIGS. 6-8 are illustrative inputs and outputs of the graphical elementselection system 124, according to example embodiments. As shown ingraphical user interface 610, the messaging client application 104presents a list of third-party applications 105 that are configured toshare and provide graphical elements to the messaging client application104. The applications in the list shown are installed on the user deviceon which the messaging client application 104 is installed. Eachapplication on the list is presented with a connect option to allow theuser to connect the third-party application 105 with the messagingclient application 104. For example, a first third-party application 105is presented with a connect option 612.

In response to receiving a user selection of the connect option 612, themessaging client application 104 communicates with the first third-partyapplication 105 to authenticate and begin sharing authentication andgraphical element information with the first third-party application105. In some implementations, this is performed in accordance with theOATH 2 framework. After the first third-party application 105 isconnected to the messaging client application 104, the first third-partyapplication 105 provides an initial set of graphical elements, generatedby the first third-party application 105, to the messaging clientapplication 104. This initial list of graphical elements may be adefault list and may not be based on user interactions with the firstthird-party application 105. In some embodiments, the initial list ofgraphical elements provided by the first third-party application 105 maybe provided by the first third-party application 105 based on a recentset of interactions the user performed with the first third-partyapplication 105.

The messaging client application 104 presents the list of graphicalelements received from the first third-party application 105 and/or thegraphical elements selected based on data received from the firstthird-party application 105 in a dedicated region 620 of a browsinginterface. Dedicated region 620 may be a separate region of thegraphical user interface of the messaging client application 104 forpresenting graphical elements associated with the first third-partyapplication 105. Other dedicated regions (not shown) for presentinggraphical elements associated with other applications may also beincluded together with the dedicated region 620.

Along with the graphical elements in the dedicated region associatedwith the first third-party application 105, the messaging clientapplication 104 presents a second set of graphical elements 622. Thesecond set of graphical elements 622 may be associated with graphicalelements generated by the messaging client application 104 and/oranother third-party application 105. In an embodiment, the graphicalelements presented in dedicated region 620 and/or the second set ofgraphical elements 622 may be dynamically ordered based on contextinformation received from one or more third-party applications 105(e.g., the first third-party application 105).

In some embodiments, at a later point in time or an earlier point intime, the messaging client application 104 may receive a communicationfrom the first third-party application 105 indicating that no graphicalelements are available. For example, the first third-party application105 may determine that a period of user inactivity has been exceeded.Specifically, if the first third-party application 105 determines thatthe user has not performed any interactions with the first third-partyapplication 105 for more than 24 hours, the first third-partyapplication 105 may inform the messaging client application 104 toremove some or all of the graphical elements associated with the firstthird-party application 105. In such cases, the messaging clientapplication 104 presents a graphical user interface shown in FIG. 7 withan indicator 710 in the dedicated region 620. The indicator may informthe user that no graphical elements are currently available from thefirst third-party application 105. At a later time, the user can accessthe first third-party application 105 and perform a user interaction. Inresponse, the first third-party application 105 communicates the userinteraction and/or graphical element associated with the interaction tothe messaging client application 104. As a result, the dedicated region620 is updated to now include the graphical elements associated with themost recent interaction.

In some embodiments, the messaging client application 104 receives auser selection of a graphical element form the browser interface. Inresponse, the messaging client application 104 presents a screen 720that allows the user to capture an image or video and/or retrieve animage or video previously stored and modify the image or video using theselected graphical element. The user can select a send option 722 tocause the messaging client application 104 to send the modified image orvideo to a designated recipient.

In some embodiments, the messaging client application 104 presents achat interface 810, as shown in FIG. 8. The chat interface allows afirst user to communicate and exchange messages with a second user.During the chat session, the first user may request to view a list ofgraphical elements. In response, the messaging client application 104presents a list of graphical elements 820 together with the chatinterface (e.g., on the bottom of the chat interface). The list includesone or more graphical elements associated with a third-party application105. For example, the list may include a graphical element received fromthe third-party application 105. In an embodiment, the list isdynamically updated based on user interactions received from thethird-party application 105. In response to receiving a user selectionof a given graphical element from the list of graphical elements 820,the messaging client application 104 automatically transmits the givengraphical element to the second user in the chat interface.

In some embodiments, the list of graphical elements 820 may beorganized, grouped, or separated into regions. Each region of the listof graphical elements 820 may be dedicated to presenting graphicalelements from a respective third-party application 105. Each region mayprovide an identifier of the third-party application 105 from which thegraphical elements were received or with which the graphical elementsare associated.

FIG. 9 is a block diagram illustrating an example software architecture906, which may be used in conjunction with various hardwarearchitectures herein described. FIG, 9 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 906 may execute on hardwaresuch as machine 1000 of FIG. 10 that includes, among other things,processors 1004, memory 1014, and input/output (I/O) components 1018. Arepresentative hardware layer 952 is illustrated and can represent, forexample, the machine 1000 of FIG. 10. The representative hardware layer952 includes a processing unit 954 having associated executableinstructions 904. Executable instructions 904 represent the executableinstructions of the software architecture 906, including implementationof the methods, components, and so forth described herein. The hardwarelayer 952 also includes memory and/or storage modules memory/storage956, which also have executable instructions 904. The hardware layer 952may also comprise other hardware 958.

In the example architecture of FIG. 9, the software architecture 906 maybe conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 906 mayinclude layers such as an operating system 902, libraries 920,frameworks/middleware 918, applications 916, and a presentation layer914. Operationally, the applications 916 and/or other components withinthe layers may invoke API calls 908 through the software stack andreceive messages 912 in response to the API calls 908. The layersillustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile or specialpurpose operating systems may not provide a frameworks/middleware 918,while others may provide such a layer. Other software architectures mayinclude additional or different layers.

The operating system 902 may manage hardware resources and providecommon services. The operating system 902 may include, for example, akernel 922, services 924, and drivers 926. The kernel 922 may act as anabstraction layer between the hardware and the other software layers.For example, the kernel 922 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 924 may provideother common services for the other software layers. The drivers 926 areresponsible for controlling or interfacing with the underlying hardware.For instance, the drivers 926 include display drivers, camera drivers.Bluetooth® drivers, flash memory drivers, serial communication drivers(e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audiodrivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 920 provide a common infrastructure that is used by theapplications 916 and/or other components and/or layers. The libraries920 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 902 functionality (e.g., kernel 922,services 924 and/or drivers 926). The libraries 920 may include systemlibraries 944 (e.g., C standard library) that may provide functions suchas memory allocation functions, string manipulation functions,mathematical functions, and the like. In addition, the libraries 920 mayinclude API libraries 946 such as media libraries (e.g., libraries tosupport presentation and manipulation of various media format such asMPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., anOpenGL framework that may be used to render two-dimensional andthree-dimensional in a graphic content on a display), database libraries(e.g., SQLite that may provide various relational database functions),web libraries (e.g., WebKit that may provide web browsingfunctionality), and the like. The libraries 920 may also include a widevariety of other libraries 948 to provide many other APIs to theapplications 916 and other software components/modules.

The frameworks/middleware 918 (also sometimes referred to as middleware)provide a higher-level common infrastructure that may be used by theapplications 916 and/or other software components/modules. For example,the frameworks/middleware 918 may provide various graphic user interfacefunctions, high-level resource management, high-level location services,and so forth. The frameworks/middleware 918 may provide a broad spectrumof other APIs that may be utilized by the applications 916 and/or othersoftware components/modules, some of which may be specific to aparticular operating system 902 or platform.

The applications 916 include built-in applications 938 and/orthird-party applications 940. Examples of representative built-inapplications 938 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 940 may include anapplication developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 940 may invoke the API calls 908 provided bythe mobile operating system (such as operating system 902) to facilitatefunctionality described herein.

The applications 916 may use built-in operating system functions (e.g.,kernel 922, services 924, and/or drivers 926), libraries 920, andframeworks/middleware 918 to create UIs to interact with users of thesystem. Alternatively, or additionally, in some systems, interactionswith a user may occur through a presentation layer, such as presentationlayer 914. In these systems, the application/component “logic” can beseparated from the aspects of the application/component that interactwith a user.

FIG. 10 is a block diagram illustrating components of a machine 1000,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 10 shows a diagrammatic representation of the machine1000 in the example form of a computer system, within which instructions1010 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1000 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1010 may be used to implement modules or componentsdescribed herein. The instructions 1010 transform the general,non-programmed machine 1000 into a particular machine 1000 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1000 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1000 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1000 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1010, sequentially or otherwise, that specify actions to betaken by machine 1000. Further, while only a single machine 1000 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1010 to perform any one or more of the methodologiesdiscussed herein.

The machine 1000 may include processors 1004, memory/storage 1006, andI/O components 1018, which may be configured to communicate with eachother such as via a bus 1002. In an example embodiment, the processors1004 (e.g., a central processing unit (CPU), a reduced instruction setcomputing (RISC) processor, a complex instruction set computing (CISC)processor, a graphics processing unit (GPU), a digital signal processor(DSP), an application-specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), another processor, or anysuitable combination thereof) may include, for example, a processor 1008and a processor 1012 that may execute the instructions 1010. The term“processor” is intended to include multi-core processors 1004 that maycomprise two or more independent processors (sometimes referred to as“cores”) that may execute instructions contemporaneously. Although FIG.10 shows multiple processors 1004, the machine 1000 may include a singleprocessor with a single core, a single processor with multiple cores(e.g., a multi-core processor), multiple processors with a single core,multiple processors with multiple cores, or any combination thereof.

The memory/storage 1006 may include a memory 1014, such as a mainmemory, or other memory storage, and a storage unit 1016, bothaccessible to the processors 1004 such as via the bus 1002. The storageunit 1016 and memory 1014 store the instructions 1010 embodying any oneor more of the methodologies or functions described herein. Theinstructions 1010 may also reside, completely or partially, within thememory 1014, within the storage unit 1016, within at least one of theprocessors 1004 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine1000. Accordingly, the memory 1014, the storage unit 1016, and thememory of processors 1004 are examples of machine-readable media.

The I/O components 1018 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1018 that are included in a particular machine 1000 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1018 may include many other components that are not shown inFIG. 10. The I/O components 1018 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 1018may include output components 1026 and input components 1028. The outputcomponents 1026 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1028 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1018 may includebiometric components 1039, motion components 1034, environmentalcomponents 1036, or position components 1038 among a wide array of othercomponents. For example, the biometric components 1039 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1034 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1036 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g,,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1038 mayinclude location sensor components (e.g., a GPS receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1018 may include communication components 1040operable to couple the machine 1000 to a network 1037 or devices 1029via coupling 1024 and coupling 1022, respectively. For example, thecommunication components 1040 may include a network interface componentor other suitable device to interface with the network 1037. In furtherexamples, communication components 1040 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1029 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 1040 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1040 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1040, such as location via Internet Protocol (IP) geo-location, locationvia Wi-Fi® signal triangulation, location via detecting a NFC beaconsignal that may indicate a particular location, and so forth.

Glossary:

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying transitory or non-transitoryinstructions for execution by the machine, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such instructions. Instructions may be transmitted orreceived over the network using a transitory or non-transitorytransmission medium via a network interface device and using any one ofa number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, PDA, smart phone,tablet, ultra book, netbook, laptop, multi-processor system,microprocessor-based or programmable consumer electronics, game console,set-top box, or any other communication device that a user may use toaccess a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network andthe coupling may be a Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or other typeof cellular or wireless coupling. In this example, the coupling mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1×RTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (CPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UMTS), High Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term Evolution (LTE)standard, others defined by various standard setting organizations,other long range protocols, or other data transfer technology.

“EPHEMERAL MESSAGE” in this context refers to a message that isaccessible for a time-limited duration. An ephemeral message may be atext, an image a video, and the like. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, device,or other tangible media able to store instructions and data temporarilyor permanently and may include, but is not limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity, orlogic having boundaries defined by function or subroutine calls, branchpoints, APIs, or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein.

A hardware component may also be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware component may include dedicated circuitry or logic that ispermanently configured to perform certain operations. A hardwarecomponent may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an ASIC. A hardware componentmay also include programmable logic or circuitry that is temporarilyconfigured by software to perform certain operations. For example, ahardware component may include software executed by a general-purposeprocessor or other programmable processor. Once configured by suchsoftware, hardware components become specific machines (or specificcomponents of a machine) uniquely tailored to perform the configuredfunctions and are no longer general-purpose processors. It will beappreciated that the decision to implement a hardware componentmechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations. Accordingly, the phrase“hardware component”(or “hardware-implemented component”) should beunderstood to encompass a tangible entity, be that an entity that isphysically constructed, permanently configured (e.g., hardwired), ortemporarily configured (e.g., programmed) to operate in a certain manneror to perform certain operations described herein. Consideringembodiments in which hardware components are temporarily configured(e.g., programmed), each of the hardware components need not beconfigured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processorconfigured by software to become a special-purpose processor, thegeneral-purpose processor may be configured as respectively differentspecial-purpose processors (e.g., comprising different hardwarecomponents) at different times. Software accordingly configures aparticular processor or processors, for example, to constitute aparticular hardware component at one instance of time and to constitutea different hardware component at a different instance of time.

Hardware components can provide information to, and receive informationfrom, other hardware components. Accordingly, the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between such hardwarecomponents may be achieved, for example, through the storage andretrieval of information in memory structures to which the multiplehardware components have access. For example, one hardware component mayperform an operation and store the output of that operation in a memorydevice to which it is communicatively coupled. A further hardwarecomponent may then, at a later time, access the memory device toretrieve and process the stored output.

Hardware components may also initiate communications with input oroutput devices and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands,” “op codes,” “machine code,” etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a CPU, a RISC processor, a CISCprocessor, a GPU, a. DSP, an ASIC, a RFIC or any combination thereof. Aprocessor may further be a multi-core processor having two or moreindependent processors (sometimes referred to as “cores”) that mayexecute instructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, forexample giving date and time of day, sometimes accurate to a smallfraction of a second.

Changes and modifications may be made to the disclosed embodimentswithout departing from the scope of the present disclosure. These andother changes or modifications are intended to be included within thescope of the present disclosure, as expressed in the following claims.

Whats claimed is:
 1. A method comprising: receiving, with a messagingapplication implemented by one or more processors of a user device, acommunication from a given application representing a first userinteraction with the given application; generating, with the messagingapplication, a list of graphical elements based on the communicationreceived from the given application; displaying, with the messagingapplication, the list of graphical elements; receiving, with themessaging application, a user selection of a first graphical elementfrom the list of graphical elements; and incorporating, with themessaging application, the graphical element selected by the user into amessage for transmission to another user.
 2. The method of claim 1,wherein the communication includes a second graphical element; andwherein generating the list of graphical elements comprises combiningthe second graphical element received in the communication from thegiven application with one or more other graphical elements generated bythe messaging application.
 3. The method of claim 1, wherein generatingthe list of graphical elements comprises dynamically ordering the listof graphical elements based on the first user interaction with the givenapplication.
 4. The method of claim 3, wherein a second graphicalelement in the list of graphical elements is in a first position in thelist of graphical elements at a first point in time and is positionedlower in the list of graphical elements at a second point in time laterthan the first point in time.
 5. The method of claim 1, furthercomprising: receiving, with the messaging application, anothercommunication from the given application representing a second userinteraction with the given application; determining that the second userinteraction took place more recently than the first user interaction;and in response to determining that the second user interaction tookplace more recently than the first user interaction, positioning asecond graphical element in the list of graphical elements associatedwith the first user interaction at a lower position in the list ofgraphical elements than a third graphical element associated with thesecond user interaction.
 6. The method of claim 5, wherein the firstuser interaction represents a first song played by the givenapplication, wherein the second user interaction represents a secondsong played by the given application after the first song; and whereinthe second graphical element identifies the first song and the thirdgraphical element identifies the second song.
 7. The method of claim 1,wherein displaying, with the messaging application, the list ofgraphical elements comprises displaying the list of graphical elementswithin a graphical user interface dedicated to presenting graphicalelements or within a chat interface of the messaging application.
 8. Themethod of claim 1, wherein incorporating, with the messagingapplication, the graphical element into the message comprises sending achat message to the another user or adding the graphical element to animage that is sent to the another user.
 9. The method of claim 1,wherein one or more of the graphical elements in the list of graphicalelements is associated with a universal resource locator (URL) thatcauses content associated with the corresponding one or more of thegraphical elements to be presented.
 10. The method of claim 1, wherein:the messaging application is provided by a first entity or organization;and the given application is provided by a second entity or organizationdifferent from the first entity or organization.
 11. The method of claim1, wherein the given application is configured to share theauthentication information with the messaging application based on anOAuth 2 authorization framework; and wherein the graphical elementsinclude at least one of an image, a video, an animation, or a referenceto content.
 12. The method of claim 1, further comprising: displayingwith the messaging application a list of applications that are availableto provide graphical elements to the messaging application; andconnecting the messaging application with the given application in thelist of applications in response to receiving a user selection of thegiven application.
 13. The method of claim 1, wherein displaying, withthe messaging application, the list of graphical elements comprises:displaying a first set of the graphical elements in the list ofgraphical elements in a first region dedicated to presenting graphicalelements associated with the given application; and displaying a secondset of the graphical elements in the list of graphical elements in asecond region dedicated to presenting graphical elements associated witha second application.
 14. The method of claim 13, further comprising:determining that no graphical elements are currently associated with athird application; and displaying an indicator in a third regiondedicated to presenting graphical elements associated with the thirdapplication, the indicator indicating that no graphical elements arecurrently associated with the third application.
 15. The method of claim1, wherein the communication received from the given applicationincludes ranking information; and wherein the list of graphical elementsis ranked based on the ranking information received from the givenapplication.
 16. The method of claim 1, wherein the communicationreceived from the given application includes duration of the first userinteraction; and wherein the list of graphical elements is ranked basedon the duration of the first user interaction.
 17. The method of claim1, wherein the given application is an exercise application, wherein thefirst user interaction corresponds to exercise performed by the usertracked by the exercise application; and wherein the communicationincludes a second graphical element that represents a type of exerciseperformed by the user and a metric or statistic associated with theexercise performed by the user.
 18. A system comprising: a processorconfigured to perform operations comprising: receiving, with a messagingapplication implemented by one or more processors of a user device, acommunication from a given application representing a first userinteraction with the given application; generating, with the messagingapplication, a list of graphical elements based on the communicationreceived from the given application; displaying, with the messagingapplication, the list of graphical elements; receiving, with themessaging application, a user selection of a first graphical elementfrom the list of graphical elements; and incorporating, with themessaging application, the graphical element selected by the user into amessage for transmission to another user.
 19. The system of claim 1,wherein the communication includes a second graphical element; andwherein generating the list of graphical elements comprises combiningthe second graphical element received in the communication from thegiven application with one or more other graphical elements generated bythe messaging application.
 20. A non-transitory machine-readable storagemedium that includes instructions that, when executed by one or moreprocessors of a machine, cause the machine to perform operationscomprising: receiving, with a messaging application implemented by oneor more processors of a user device, a communication from a givenapplication representing a first user interaction with the givenapplication; generating, with the messaging application, a list ofgraphical elements based on the communication received from the givenapplication; displaying, with the messaging application, the list ofgraphical elements; receiving, with the messaging application, a userselection of a first graphical element from the list of graphicalelements; and incorporating, with the messaging application, thegraphical element selected by user into a message for transmission toanother user.